E2E Test Selection:
The changes are limited to CI infrastructure files: .github/workflows/build-android-e2e.yml (critical) and bitrise.yml. Although no application source code was modified, changes to the Android E2E workflow directly impact how Detox tests are built, executed, and reported in CI. This introduces systemic risk: build configuration, environment variables, caching, emulator setup, artifact handling, or test execution steps may affect all E2E suites.

Because this workflow is responsible for running Android E2E tests, the safest validation strategy is to execute the full smoke test suite to ensure:

• The Android app builds correctly in CI
• Detox setup and device/emulator boot works
• Test sharding or tagging logic (if modified) does not exclude suites
• No environment regressions affect specific feature areas (e.g., Snaps, Browser, Multi-chain, Seedless onboarding)

Since infrastructure changes can silently break subsets of tests (e.g., network mocking, feature flags, experimental builds like Card, Solana support, Snaps), running all smoke tags minimizes the risk of undetected CI regressions.

No application runtime logic was modified, so feature-specific narrowing is not appropriate here—the risk is cross-cutting across all test domains.

Performance tests are not required because:

• No app source code changed
• No UI, controller, rendering, or data-loading logic was modified
• No performance test infrastructure under tests/performance/ was changed

Thus, only functional E2E validation of the CI pipeline is needed.

Performance Test Selection:
No application code or performance test infrastructure was modified. Workflow/CI changes do not affect runtime performance characteristics of the app itself.